Operator Shift Planning

OPERATOR SHIFT PLANNING

Operator Shift Planning helps you plan, view, delete, and clone operator assignments for machines across shifts and dates.
This module ensures accurate machine–operator mapping, especially for night shifts, overlapping shifts, and cloning scenarios.

1. Planning Operator Shifts

1.1 Access Operator Shift Planning

Step 1: Navigate to the screen

From the main menu, go to Operations → Operator Shift Planning
By default, the screen opens in Plan Mode

1.2 Select Planning Mode

At the top of the screen, choose the required mode:

Plan – Create new operator shift plans
View – View or delete existing plans
Clone – Copy plans from one date to another date range

Each mode displays its own description and relevant UI automatically.

1.3 Select Date Range (Planning Mode)

Mandatory Fields

Start Date – First date of planning
End Date – Last date of planning

Important Rules

The date range cannot exceed 15 days
End Date cannot be earlier than Start Date
If the range exceeds 15 days, a red warning message is shown and planning is disabled

1.4 Exclusion Options

You can exclude specific days from planning:

Exclude Sundays
Automatically removes all Sundays from the selected date range
Exclude Specific Dates
Select individual dates to exclude (holidays, maintenance days, etc.)

Excluded dates appear as removable tags below the selection.

⚠️ IMPORTANT – Operator Selection Validation

When the option “Hide selected operators in other rows” is enabled:

Once an Operator is selected in a row, that same operator will NOT appear in the Operator dropdown of other rows.

This prevents duplicate operator assignment within the same planning session.

The operator remains visible only in the row where it is selected.

If the operator is deselected or the row is removed, the operator becomes available again in other rows.

Impact:

Ensures clean and accurate shift planning

Prevents accidental duplicate operator assignment

Reduces validation errors before saving

⚠️ Note:
If this option is unchecked, all operators will be visible in every row and duplicates are allowed (subject to validation).

1.5 Shift Details (Row-Level Planning Excel type screen)

Click Add Row to define operator assignments.

Each row contains:

Operator (Mandatory)
Machine (Mandatory)
Shift (Mandatory)
From Time (Mandatory)
To Time (Mandatory)

Important Planning Rules & Auto-Mappings

1️⃣ Shift Time Auto-Population (From Shift Master)

When a Shift is selected from the Shift dropdown, the system automatically populates:
- From Time
- To Time
These timings are fetched directly from the Shift Master configuration.

Why this matters:

This mapping is mandatory to accurately calculate IoT-based Operator OEE (Overall Equipment Effectiveness).
Manual changes to shift time should only be done when explicitly allowed by business rules.

ℹ️ Note:
IoT Operator OEE calculations depend on this exact shift timing.
Incorrect shift timing may lead to inaccurate OEE reports.

The Operator dropdown displays only operators role mapped user from User Master.

Benefits:

Ensures only operators are assigned
Prevents assignment of inactive
Improves data integrity for attendance and IoT tracking

The Machine dropdown lists only active machines.
Inactive or decommissioned machines are automatically excluded.

Benefits:

Prevents planning on unavailable machines
Ensures accurate machine utilization data
Avoids downstream IoT data inconsistencies

Summary

✅ Shift times are auto-filled from Shift Master
✅ Operator list is filtered by active user access
✅ Machine list shows only active machines
✅ These validations ensure accurate IoT Operator OEE calculations

Rules

Maximum 50 rows can be added at a time
A new row can be added only if the last row is valid
When adding a new row:
- Shift and time values are auto-copied from the previous row
- Operator and Machine can be changed if required

1.6 Shift Timing Rules

Normal Shifts

From Time must be earlier than To Time
Example: 08:00 → 17:00

Overnight / Overlapping Shifts

If Is Shift Timing Overlap = Yes
- Shifts crossing midnight are allowed
  Example: 17:30 → 01:30
- To Time is automatically saved as next day

Third Shift (Early Morning)

If Shift Report Day Detail = Previous Day(Check the Shift Master)
- Both From Time and To Time are saved on the next day Example:
  Shift Date: Dec 1
  Time: 01:30 → 08:30
  Stored as: Dec 2 01:30 → Dec 2 08:30

1.7 Validation Rules (Planning)

An operator can work on multiple machines at the same time
A machine cannot have more than one operator at the same time
Overlapping assignments for the same machine are strictly blocked
Row-level validation happens:
- On Add Row
- Before Save
- Optionally via async DB validation

Validation status is shown per row:

OK – Ready to save
Error – Hover to see the exact message
Pending – Awaiting validation

1.8 Save Planning

Click Save Shift Planning:

Data is saved in bulk for all valid dates
Backend performs final validation
After save, IoT control tasks are updated asynchronously( IF IoT Production Count Data Already Capture in DMeX)
UI does not wait for IoT sync to complete

2. View & Delete Operator Planning

2.1 Switch to View Mode

Select View from the mode toggle.

2.2 Search Planned Data

Search filters:

From Date (Mandatory)
To Date (Mandatory)

Rules

Maximum date range allowed: 31 days

2.3 View Results

Search results display:

Date
Machine Name
Operator Name
Shift Name
From Time
To Time

2.4 Delete Options

Delete Selected
- Select individual rows and delete them
Delete Entire Range
- Deletes all planning data within the selected date range

⚠️ Deletion is a hard delete and cannot be undone.

3. Clone Operator Planning

3.1 Switch to Clone Mode

Select Clone from the mode toggle.

3.2 Clone Source Date

Select Clone From Date
System checks:
- If planning exists on that date
- If no data exists → shows “No data to clone”

3.3 Select Target Date / Range

Options:

Single to Range
Clone one date to a full date range

3.4 Clone Rules

Target date(s) must not already have any planning data
If data exists in the target range:
- Clone is blocked
- User is notified
Clone always copies full day planning
Partial-day clone is not allowed

3.5 Shift Behavior During Clone

All shift rules apply during cloning:

Overnight shifts move To Time to next day
Third shift respects Shift Report Day Detail
Total time remains unchanged
Machine–operator conflicts are validated

3.6 Clone Execution

After validation:

Records are cloned in bulk
Summary is shown:
- Source Date
- Target Date / Range
- Total records cloned

4. Summary of Key Rules

Feature	Rule
Planning Date Range	Max 15 days
View Date Range	Max 31 days
Rows per Save	Max 50
Machine Assignment	Only one operator per time
Operator Assignment	Multiple machines allowed
Overnight Shift	Allowed if overlap enabled
Third Shift	Saved to next day
Clone Source	Must have data
Clone Target	Must be empty

5. Best Practices for Users

Plan shifts in smaller date ranges for clarity
Use Clone for repetitive schedules
Always validate rows before saving
Use View Mode before cloning to avoid conflicts

That’s it!
You now know how to Plan, View, Delete, and Clone Operator Shift Planning efficiently.

If you need help, please contact the support team.